Payment Delegation and Linking System

ABSTRACT

Methods, systems, devices, and computer-readable media for a payment delegation and linking system are provided. The system may generate a delegation request to send to an individual for payment of a portion of a value of a transaction. The delegation request may be sent to the individual with a payment URL embedded with a token. Upon initiation of payment in response to the delegation request, the token may be embedded in an unused field of a payment transaction record generated at the individual&#39;s device and may be transmitted from the individual&#39;s device to a payment processing system for processing and settlement. The payment transaction record may ultimately be received at the requestor&#39;s bank with the token intact. The token may be used to link the received payment transaction with the original delegated transaction. The original delegated transaction and the received payment transaction may be displayed together in a transaction summary.

FIELD OF USE

Aspects of the disclosure relate generally to payment delegationmethods, and more particularly to methods of linking received delegatedpayments to an original transaction.

BACKGROUND

While some merchants, such as restaurants, may break transactions intomultiple payment portions for the sake of consumer convenience, splitpayments among many individuals is primarily a trick of accountingsoftware or applications, which simply divide a transaction by dollaramount into individual transactions. However, when the number of desiredpayors increases, the time spent breaking apart a transaction becomeshigh and a risk of mistakes increases. Ultimately, when processed, thefinal payment and reconciliation of funds occurs as a function of asingle payor making a single payment for each of the individualtransactions. Existing systems are limited, however, in their ability toallow a single payor to redirect payments for a given transaction toother payors during a post-payment experience and to manage receipt ofpayment from such other payors in a manner that allows the originalpayor to recognize that the received payments are associated with theoriginal transaction.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of various aspects of the disclosure. The summary is notan extensive overview of the disclosure. It is neither intended toidentify key or critical elements of the disclosure nor to delineate thescope of the disclosure. The following summary merely presents someconcepts of the disclosure in a simplified form as a prelude to thedetailed description below.

Aspects of the disclosure relate to systems, apparatuses,computer-readable media, and methods for facilitating the delegation ofpartial payments for a purchase transaction and linking receivedpayments back to the original purchase transaction. A user may purchasean item and wish to share the cost of that purchase with one or moreother individuals. The user, post-payment, may use a banking applicationto request partial payment from the one or more individuals directlyfrom the transaction account from which the user made payment.Delegation requests for the partial payments may be sent to the one ormore individuals, and the delegation requests may be embedded with apayment token used to link received payments from the one or moreindividuals to the original purchase transaction. When the individualsinitiate payment to the user, the embedded token may be stored in anunused field of a payment transaction record transmitted to a paymentprocessor for processing and settlement. The payment transaction recordmay ultimately be received at the user's bank with the payment tokenintact. The payment token may be used to link the received paymenttransaction with the original purchase transaction. The originalpurchase transaction and any corresponding received delegated paymentsmay be displayed together in the banking application.

These and other features and advantages of the disclosure will beapparent from the detailed description provided below.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 illustrates an example payment delegation and linking process, inaccordance with one or more aspects described herein.

FIG. 2 is a diagram of an example computing environment for a paymentdelegation and linking system, in accordance with one or more aspectsdescribed herein.

FIG. 3 illustrates an example computing device for use in a paymentdelegation and linking system, in accordance with one or more aspectsdescribed herein.

FIGS. 4A-4G depict an example sequence for performing payment delegationand linking functions, in accordance with one or more aspects describedherein.

FIGS. 5A-5J are example user interfaces used in performing paymentdelegation and linking functions, in accordance with one or more aspectsdescribed herein.

FIGS. 6A-6B are example payment transaction records used in performingpayment delegation and linking functions, in accordance with one or moreaspects described herein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings, which form a part hereof, and inwhich is shown, by way of illustration, various embodiments in whichaspects of the disclosure may be practiced. It is to be understood thatother embodiments may be utilized and structural and functionalmodifications may be made without departing from the scope of thepresent disclosure. Aspects of the disclosure are capable of otherembodiments and of being practiced or being carried out in various ways.In addition, it is to be understood that the phraseology and terminologyused herein are for the purpose of description and should not beregarded as limiting. Rather, the phrases and terms used herein are tobe given their broadest interpretation and meaning.

Aspects described herein improve the functioning of computers byimproving the process by which shared payments are processed andmanaged. At present, sharing payments with others is time-consuming,subject to human error particularly when payment needs to be made bymultiple individuals, and lacking in the ability to connect receivedpayments with an original transaction at the source. Current systems areunable to address this problem, because such systems are generallythird-party systems employed to assist users in requesting splitpayments. Because such third-party systems are not source systems, e.g.,they do not source the transaction, they do not have access to theinformation or data necessary to actively manage receipt of splitpayments and associate such received payments with their originalcounterpart transactions. When split payments are received by suchsystems they are received as non-descript transactions with no means foridentifying or connecting the payments with an original transaction forwhich a request for payment was made. By providing computers, associatedwith financial institutions such as banks, with the ability to manageand link received split payments with a corresponding originaltransaction, organizations, such as financial institutions, may be ableto seamlessly provide users with an efficient and convenient means ofmanaging their own financial data. Such improved systems simplify thetransaction splitting process for both the merchant and the consumer.The merchant does not need to maintain splitting software and manage thereceipt of multiple payments from multiple consumers for a singletransaction and, instead, is able to process and receive payment from asingle consumer for a single transaction. And the consumer is providedwith a single source—the consumer's bank—for managing splitting requestsand for receipt of payments associated with such requests. The consumeris able to conveniently manage the splitting of transactions, at theirprimary source, directly through the consumer's banking application.

Aspects discussed herein may relate to methods, systems, devices, andcomputer-readable media for a payment delegation and linking system.

Referring to FIG. 1, an example payment delegation and linking processis illustrated. Initially, a user may make a payment to a merchantusing, for example, a debit card or a credit card for a purchase madewith the merchant. The merchant may send the payment to a transaction orpayment processing system for coordinating settlement between themerchant bank and the user's bank. For instance, the payment processingsystem will coordinate receiving payment from the user's bank andsending the payment to the merchant's bank. From the user's perspective,upon settlement a record associated with the user's purchase transactionmay be received at the user's bank and may be stored in a database, suchas a transaction database maintained by the bank, and the user's bankaccount may be debited for the amount of the purchase. The user maythereafter access his bank account through a banking applicationexecuting on a user device or on a website associated with the user'sbank and may view the various transactions associated with the user'sbank account. The user may make a selection of a transaction, via thebanking application, and may request that the selected transaction besplit amongst one or more other individuals. For instance, the user maywish to split the cost of a lunch purchased for himself and somefriends. The user may select one or more contacts from his user device,or from an account, such as a social media account, associated with theuser, or may enter contact information for individuals with whom hewould like to split the selected transaction. The user may furtherdesignate specific amounts to request from each of the selectedindividuals. For example, if the lunch bill were $50, the user mayrequest $20 from a first individual and $15 from a second individual.After designating specific amounts to each of the selected individuals,the user may submit a request to send a delegation request for thedesignated payment amounts to each of the selected individuals. Ascript, such as an application programming interface (API), providing aninterface between the banking application and a payment delegationserver maintained by the bank, may be executed to generate a paymenttoken which uniquely identifies the delegated transaction. The paymenttoken may be stored together with the delegated transaction in thetransaction database, for instance in a memo field or other unused fieldassociated with the delegated transaction. The script and/or API mayadditionally generate a payment uniform resource identifier (URL) foreach of the selected individuals, i.e., the delegates. The payment URLmay include parameters containing information about the delegationrequest as it pertains to the individual delegate for whom the URL isgenerated. For instance, the information may identify the requestorusing a name, email address, phone number, or the like, identify theoriginal/delegated transaction by name or description, indicate a totalpayment amount delegated to the individual, and identify a financialinstitution/account where payment should be sent. The URL parameters mayadditionally include the generated payment token identifying thedelegated transaction. A message including a corresponding generatedpayment URL may be sent to each of the delegates indicating that theuser requests payment for the designated amount. The delegates may eachreceive, at a corresponding delegate device, a message requestingpayment and may initiate payment by selecting the payment URL includedin the message. Selecting the payment URL may cause a script, such as anAPI, to execute at the delegate device. The script executing at delegatedevice may cause an application associated with a default payment methodused by the delegate's device to be executed. The script may furthercause payment fields associated with the payment application to beprepopulated with the information sent in the payment URL, such as arequestor name, email address, or phone number, a payment amount,information indicating where the payment should be sent, etc. Thedelegate may make adjustments as needed, such as changing the paymentamount to a different amount. The script may additionally cause apayment transaction record generated by the payment application andassociated with the delegate's payment to be embedded with the paymenttoken that was sent in the payment URL. The payment token may beembedded in an unused field of the payment transaction record. As aresult, when the delegates send their payment, the payment transactionrecord may be sent to the payment processing system with the paymenttoken embedded therein. The payment processing system may thencoordinate settlement between the delegate's bank and the user's bank.When the delegate's payment is eventually received at user's bank, thepayment transaction may be stored in the bank's transaction database andthe user's account may be credited for the payment amount. Further, uponreceiving the payment transaction, the payment token embedded in thepayment transaction may be detected. Such a detection may indicate thatthe received payment transaction is associated with another transactionfor which the user requested delegated payments. The payment token maybe used to identify the original/delegated transaction and the paymenttransaction may then be linked to the original transaction. The user maybe notified that a payment associated with a delegated transaction hasbeen received and the user may access his online bank account, via thebanking application, to view the original transaction together with anyreceived payments from the delegates showing as linked with the originaltransaction. For example, the delegated transaction may be displayedwith all payments received from delegates underneath. Alternatively, theuser may select the delegated transaction and a list of all requestedpayments received from delegates may be displayed in response. In thisway, a user may easily and conveniently track payments received inconnection with a request to delegate payment for a given transaction.

Referring to FIG. 2, an example computing environment for a paymentdelegation and linking system 100 is provided. The payment delegationand linking system 100 may include one or more systems or computingdevices, such as a transaction server 110, a payment delegation database120, a database 130, one or more user computing devices 140 (e.g., afirst user computing device 140 a and/or a second user computing device140 b), one or more delegate computing devices 150, a payment processingsystem 160, a private network 170, and a private network 180. Althoughthe various systems and computing devices in the computing environment100 are shown and described as separate devices, one or more of thecomputing devices, may be part of a single computing device withoutdeparting from the disclosure.

The transaction server 110 may be a computing device, such as a server,used by a banking institution or other financial institution to providefunctionality associated with transaction processing. Users may hold atransaction account, such as a bank account, a credit card account, acommercial account, a line of credit, or the like, maintained by thebanking institution. The transaction server 110 may control processingbank transactions associated with the transactions, such as depositsmade to the account, payments made from at the account, credits and/ordebits to the account, transferring funds between accounts and/or banks,or the like. The transaction server 110 may store and/or control abanking application 111 for providing the user with online access to theuser's account.

Accordingly, the banking application 111 may be associated with theuser's bank account, credit card account, commercial account, line ofcredit, or the like. The banking application 111 may be used by the userto perform various account-related functions, such as viewing accounttransactions, making payments, depositing checks, transferring funds,sending funds, etc. Additionally or alternatively, the bankingapplication 111 may be used to facilitate splitting or delegatingportions of a transaction associated with a user's transaction account.As will be described below in further detail, the banking application111 may generate and display one of more user interfaces that allow theuser to select a transaction and provide inputs related to requestingpayments from one or more individuals for some portion of thetransaction amount, to view delegation requests, and to view delegatedpayments received for a delegated transaction. The banking application111 may be a server-based application installed and executed at thetransaction server 110. The server-based banking application 111 may beaccessed through a website, such as a banking website, by a clientdevice, such as by the second user computing devices 140 b. Additionallyor alternatively, the banking application 111 may be a client-basedapplication installed and executed on a client device, such as the firstuser computing device 140 a.

The payment delegation server 120 may be a computing device, such as aserver, used by a banking institution or other financial institution toprovide functionality associated with coordinating delegation requestsfor payment of portions of a transaction and linking received delegatepayments with an original delegated transaction. The payment delegationserver 120 may communicate with the transaction server 110 and thedatabase 130, via the private network 170, in coordinating andprocessing the delegation requests.

The database 130 may store information used by the transaction server110, the banking application 111, and/or the payment delegation server.The database 120 may comprise one or more of a relational database, ahierarchical database, a distributed database, an in-memory database, aflat file database, an XML database, a NoSQL database, a graph database,or the like.

The one or more user computing devices 140, e.g., first user computingdevice 140 a and/or the second user computing device 140 b, may beconfigured to communicate with and/or connect to one or more computingdevices of the computing environment 100 via the public network 160. Insome instances, the one or more user computing devices 140 may haveinstalled thereon one or more applications for performing one or moreaspects described herein. For instance, the first user computing device140 a may store an application, such as the banking application 111, foraccessing a bank account, credit card account, commercial account, lineof credit, or the like. In some instances, the one or more usercomputing devices 140 may access one or more applications installed onthe transaction server 110 for performing one or more aspects describedherein. For instance, the second user computing device 140 b, mayaccess, using a web site, and via the public network 180, the bankingapplication 111 installed at the transaction server 110.

The one or more user computing devices 140 may be any type of computingdevice or combination of devices capable of performing the particularfunctions disclosed herein. For example, the one or more user computingdevices 140 may be and/or include server computers, desktop computers,laptop computers, tablet computers, smart phones, fitness devices, orthe like that may include one or more processors, memories,communication interfaces, storage devices, and/or other components. Theone or more user computing devices 140, in some instances, may be orinclude special-purpose computing devices configured to perform thefunctions disclosed herein. In some instances, some or all of thefunctionality of the transaction server 110 may instead be performed byany of the one or more user computing devices 140 alone or incombination with the transaction server 110.

The one or more delegate computing devices 150 may be computing devicesassociated with delegates who receive a delegation request for paymentof a portion of a transaction. The one or more delegate computingdevices 150 may be configured to communicate with and/or connect to oneor more computing devices of the computing environment 100 via thepublic network 160. In some instances, the one or more delegatecomputing devices 150 may have installed thereon one or moreapplications for performing one or more aspects described herein. Forinstance, the first user computing device 140 a may store anapplication, such as the banking application 111, for accessing a bankaccount, credit card account, commercial account, line of credit, or thelike. In some instances, the one or more user computing devices 140 mayaccess one or more applications installed on the transaction server 110for performing one or more aspects described herein. For instance, theone or more user computing devices 150, may access, using a website, andvia the public network 180, the banking application 111 installed at thetransaction server 110. The one or more delegate computing devices 150may additionally have installed thereon, or may access via a websiteusing the public network 180, one or more payment applications formaking an electronic payment, such as PAYPAL, APPLE PAY, GOOGLE PAY,SAMSUNG PAY, ZELLE, VENMO, CASHAPP, or the like. The payment applicationmay be used to make a payment of a delegated amount to a user, inaccordance with aspects described herein.

The one or more user computing devices 140 may have integrated thereinan image capturing device for capturing an image, such as a receiptimage, or scanning a code, such as a bar code or a quick response (QR)code. For instance, the image capturing device may be one of one or moresensors of the one or more user computing devices 140, and one or moreapplications installed on the one or more user computing devices 140 maycause the image capturing device to be activated and to capture an imageor scan a code. The captured image may be stored on the one or more usercomputing devices 140 and/or on a different device. In some cases, theimage capturing device may be used to capture one or more images of areceipt for use in extracting line item data for a correspondingtransaction. In some cases, the image capturing device may be used toscan a barcode, QR code, or the like displayed on a receipt to providefurther information about the transactions provided on the receipt. Insome cases, the one or more user computing devices 140 may use an imagecapturing device that is separately embodied from the one or more usercomputing devices 140. When separately embodied, the image capturingdevice may, in some cases, be communicatively connected to the one ormore user computing devices 140 and may be controlled by the one or moreuser computing devices 140. In some instances, the image capturingdevice, might not be connected to the one or more user computing devices140. In some instances, the image capturing device may becommunicatively connected to the public network 180 and may beconfigured to transmit images to the one or more user computing devices140, the transaction server 110, and/or to other devices via the publicnetwork 180.

The payment processing system 160 may comprise one or more computingdevices associated with a payment processing network of systems anddevices associated with merchants, clearinghouses, financialinstitutions, and the like that interact with one another to process,authorize, and settle payment transactions, such as a credit cardtransaction or an Automated Clearing House (ACH) transaction. Forinstance, a credit card payment processing system may receive a requestfrom a merchant point of sale system for authorization of a purchasetransaction made with a credit card. The payment processing system 160may send information associated with the purchase transaction to asystem associated with the banking institution that issued the creditcard. The banking institution system may execute one or more processesto make an authorization determination. For example, the bankinginstitution system may assess potential fraud associated with thepurchase transaction and may confirm the account holder has sufficientcredit to cover the purchase amount. The banking institution system maysend the authorization determination back to the payment processorsystem 160 for approval or denial of the purchase transaction. Ifapproved, the payment processor system 160 may additionally coordinatepayment from the credit card issuing bank and the merchant bank. In thiscase, the credit card issuing bank may receive the purchase transactionat a transaction server and/or database, such as the transaction server110 and/or the database 130, and may perform one or more functions tocause the user's account to be credited for the payment amountassociated with the purchase transaction. Additionally, in the case ofan electronic payment processing system, such as the ACH network, when auser authorizes an ACH payment to a merchant directly from the user'sbank account, the merchant bank may send a request for payment to thepayment processing system 160 and the payment processing system 160 mayin turn send a request to the user's bank for the payment. The user'sbank may confirm whether the user has sufficient funds to make thepayment and, in this case the user's bank may receive and process thepayment transaction via a transaction server and/or database, such asthe transaction server 110 and/or the database 130, and may perform oneor more functions to cause the payment to be debited from the user'sbank account. The user's bank may further send a request to the paymentprocessor 160 to coordinate payment to the merchant bank.

The private network 170 may be a network operated by, and internal to,an organization or business, such as a banking institution. The privatenetwork 170 may be used to interconnect one or more computing devicesinternal to the organization or business. The private network 170 mayfurther connect to the public network 180. The private network 170 mayinclude one or more of local area networks (LANs), wide area networks(WANs), virtual private networks (VPNs), or the like.

The public network 180 may connect the private network 170, and/or theone or more computing devices connected thereto, to one or morenetworks, systems, and/or computing devices that might not be associatedwith the organization, such as the one or more user computing devices140 and the one or more delegate computing device 150. The publicnetwork 180 may include one or more networks, such as the Internet.

Referring to FIG. 3, an example computing device 200 is provided. Theexample computing device 200 may include or incorporate any one of thetransaction server 110, the payment delegation server 120, the database130, the one or more user computing devices 140, the one or moredelegate computing devices 150, or the payment processing system 160. Insome instances, the computing device 200 may represent, be incorporatedin, and/or include various devices such as a desktop computer, acomputer server, a mobile device, such as a laptop computer, a tabletcomputer, a smart phone, or any other types of mobile computing devices,and/or any other type of data processing device.

The computing device 200 may include one or more components, such as oneor more processors 203, a random access memory (RAM) 205, a read-onlymemory (ROM) 207, an input/output (I/O) device 209, a communicationinterface 211, one or more sensor devices 213, and a memory 215. Thecomputing device 200 may include one or more additional or differentcomponents.

The one or more processors 203 may be configured to control overalloperation of the computing device 200 and its associated components. Adata bus (not shown) may interconnect the one or more processors 203,the RAM 205, the ROM 207, the memory 215, the I/O device 209, thecommunication interface 211, and/or the one or more sensor devices 211.The one or more processors 203 may include a single central processingunit (CPU), which may be a single-core or multi-core processor, or mayinclude multiple CPUs. The one or more processors 203 and associatedcomponents may control the computing device 200 to execute a series ofcomputer-readable instructions to perform some or all of the processesdisclosed herein. Although not shown in FIG. 2, various elements withinthe memory 215 or other components in the computing device 200, mayinclude one or more caches, for example, CPU caches used by the one ormore processors 203, page caches used by operating system 217, diskcaches of a hard drive, and/or database caches used to cache contentfrom database 221. For embodiments including a CPU cache, the CPU cachemay be used by the one or more processors 203 to reduce memory latencyand access time. The one or more processors 203 may retrieve data fromor write data to the CPU cache rather than reading/writing to the memory215, which may improve the speed of these operations. In some examples,a database cache may be created in which certain data from the database221 may be cached in a separate smaller database in a memory separatefrom the database 221, such as in the RAM 205 or on a separate computingdevice. For instance, in a multi-tiered application, a database cache onan application server may reduce data retrieval and data manipulationtime by not needing to communicate over a network with a back-enddatabase server. These types of caches and others may be included invarious embodiments, and may provide potential advantages in certainimplementations of devices, systems, and methods described herein, suchas faster response times and less dependence on network conditions whentransmitting and receiving data.

The I/O device 209 may include, but need not be limited to, amicrophone, keypad, touch screen, and/or stylus, through which a user ofthe computing device 200 may provide input, and may also include one ormore of a speaker for providing audio output, and a video display devicefor providing textual, audiovisual, and/or graphical output.

The communication interface 211 may include one or more transceivers,digital signal processors, and/or additional circuitry and software forcommunicating via a network (e.g., the public network 160, the privatenetwork 170, or the like), wired or wireless, using any protocol asdescribed herein.

The one or more sensor devices 213 may include one or more of anaccelerometer, a gyroscope, a GPS device, a biometric sensor, aproximity sensor, image capturing device, a magnetometer, etc.

The memory 215 may store software to provide instructions to the one ormore processors 203 allowing the computing device 200 to perform variousactions. For example, the memory 215 may store software used by thecomputing device 200, such as the operating system 217, applications219, and/or the database 221. The various hardware memory units in thememory 215 may include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer-readable instructions, data structures,program modules, or other data. The memory 215 may include one or morephysical persistent memory devices and/or one or more non-persistentmemory devices. The memory 215 may include, but need not be limited to,the RAM 205, the ROM 207, electronically erasable programmable read onlymemory (EEPROM), flash memory, or other memory technology, optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium that may be used tostore the desired information and that may be accessed by the one ormore processors 203.

Although various components of the computing device 200 are describedseparately, functionality of the various components may be combinedand/or performed by a single component and/or multiple computing devicesin communication without departing from the disclosure.

Referring to FIGS. 4A-4G, an example event sequence for performingpayment delegation and linking functions is provided, referring FIGS.5A-5J, example user interfaces used in performing the payment delegationand linking functions are provided, and referring to FIGS. 6A and 6Bexample transaction records using in performing the payment delegationand linking functions are provided.

Referring to FIG. 4A, at step 402, a payment for a purchase may be madeto a merchant using the user computing device 140. For instance, a userof the user computing device 140 may make a payment to a merchant forgoods or services purchased from the merchant by the user. In someinstances, the user may use a payment method associated with the usercomputing device 140, such as through a mobile payment applicationinstalled on the user computing device 140. In some instances, thepayment may be made without using the user computing device 140. Forinstance, the user may make a payment to the merchant with a physicalcredit card, with a check, by wire, as an ACH payment, etc.

The payment may initially be received by a point of sale or paymentsystem associated with the merchant and the merchant payment system (notshown) may transmit the payment transaction to a payment processingsystem, such as the payment processing system 160, for processing thetransaction and coordinating the settlement process. Accordingly, atstep 404, the payment processing system 160 may receive the paymenttransaction associated with the payment made by the user to themerchant. The payment processing system 160 may be, for example, acredit card processing system, an electronic payment processing system,such as the ACH system, or the like. The payment transaction need not betransmitted directly from the user computing device 140, but may insteadbe transmitted indirectly through a merchant payment system associatedwith the merchant to whom the user made the payment. The paymentprocessing system 160 may coordinate a settlement process between a bankassociated with the merchant and a bank associated with the user.

For instance, at step 406, the payment processing system 160 maycoordinate sending transaction information to the user's bank so fundsfor payment may be debited from a payment account associated with theuser's payment method and may be transmitted to the merchant bank. Themerchant bank may credit an account associated with the merchant for thepayment amount.

At step 408, a server associated with the user's bank, such as thetransaction server 110, may receive the transaction informationassociated with the payment. The transaction information may be storedin the database 130, and the transaction server may cause the paymentaccount of the user to be debited for the payment amount. The paymentaccount may be, for example, a bank account, a credit card account, acommercial account, a line of credit, or the like.

After the payment transaction has been processed and settled, the usermay access or view the transaction through a banking applicationassociated with the payment account from which the user made the paymentfor the purchase. Accordingly, at step 410, the user may use the usercomputing device 140 to access a banking application, such as thebanking application 111, to view transactions associated with the user'spayment account. For instance, as shown in FIG. 5A, the bankingapplication 111 may output a user interface 500 a that displays a listof transactions associated with the payment account and stored in thedatabase 130.

The user may decide to split or delegate a payment amount associatedwith a purchase made by the user. For instance, the user may have paidfor lunch shared by the user and two friends. For convenience, the usermay have made a payment for the full cost of the lunch, but may wish torequest that his friends pay for their share of the lunch. At step 412,the user may make a selection, at the user computing device 140 and viathe banking application 111, of the transaction associated with apurchase the user made at Restaurant B, such as transaction 510 a shownin FIG. 5A. Selecting the transaction may cause one or more options forinteracting with selected transaction to be displayed. For instance,selecting the transaction may cause an option for splitting ordelegating the transaction to be displayed. For example, as shown inFIG. 5B, a user interface 500 b may display a split option 521associated with the selected transaction 520 a. The user may select thesplit option 521 to initiate a request to split the transaction

At step 414, the user computing device 140 may determine whether theselected transaction is an enhanced transaction having detailedtransaction information associated with the transaction and stored inthe database 130. That is, in some instances, when the transactionserver 110 initially receives the transaction, such as at step 408, thetransaction server 110 may additionally receive detailed informationabout the transaction from a merchant device associated with themerchant associated with the purchase transaction. The merchant devicemay transmit to the transaction server 110 the line item informationassociated with the purchase transaction. The line item information mayinclude a name or description of each item purchased, a price of eachitem, and/or a quantity of each item purchased. The line iteminformation may be stored together with the associated transaction inthe database 130 to enhance the commonly provided transactioninformation, which may include only a merchant name, a merchantlocation, a total amount, and payment information. In some instances,the user may upload the line item information associated with atransaction, by manually entering such information in a user interfaceprovided by the banking application 111 or by using the bankingapplication 111 to capture an image of a receipt associated with thetransaction. The banking application 111 and/or the transaction server110 may process the receipt using one or more image analysis and/orcomputer vision techniques, such as optical character recognition (OCR),object recognition, or the like, to convert one or more portions of theimage of the receipt into text. After converting the image of thereceipt to text, the user computing device 140 may analyze the convertedtext to extract the line item information from the text. In some cases,the receipt may include a bar code or QR code, which may be used toretrieve line item information from an associated merchant device. Theline item information provided by the user, manually or via the receiptupload, may be stored together with the associated transaction in thedatabase 130 to enhance the transaction. The transaction mayadditionally be flagged as an enhanced transaction to indicate thepresence of the line item information. Accordingly, at step 414, theuser computing device 140 may determine whether the transaction isflagged as an enhanced transaction.

If the user computing device 140 determines at step 414 that theselected transaction is not flagged as an enhanced transaction then,referring to FIG. 4B, at step 416, the user computing device 140 maycause the banking application 111 to output a request to the user toprovide the transaction item information associated with the selectedtransaction. In some instances, the user may be provided with a userinterface, such as user interface 500 c shown in FIG. 5C, to captureand/or upload an image of a receipt associated with the selectedtransaction.

At step 418, the user computing device 140 may receive the receipt imageand may process the receipt using one or more image analysis and/orcomputer vision techniques, such as optical character recognition (OCR),object recognition, or the like, to convert one or more portions of theimage of the receipt into text. After converting one or more portions ofthe image of the receipt to text, the user computing device 140 and/orthe transaction server 110 may analyze the converted text to extract theline item information from the text. In some instances, the receipt mayhave printed thereon a bar code or a QR code, which may be embedded withinformation identifying the receipt transaction, with the line iteminformation, and/or with a link to a script that may cause thetransaction identifying information (such as a unique transactionidentifier, the merchant name, the merchant location, a date/time of thetransaction, the transaction amount, a payment method, etc. or acombination thereof) and/or the line item information (such as adescription, an amount, a quantity, a pro rata tip amount, pro rata taxamount, or the like) to be requested and retrieved from a merchantdevice associated with a merchant associated with the receipt. In suchcases, upon capturing the image of the receipt the user computing device140 may detect the bar code or QR code and may receive or retrieve thetransaction identifying information and/or the line item informationusing the bar code or the QR code. In some instances, the user may beprovided with a user interface to manually enter the transaction itemdetails associated with the transaction. For instance, a user interfaceproviding a form for entering the details for each line item (such as adescription, an amount, a tax amount, a tip amount, or the like) may beoutput in the banking application 111.

At step 420, the user computing device 140 may cause the extracted,retrieved, or entered line item information to be stored together withthe selected transaction in the database 130. The transaction mayadditionally be flagged as an enhanced transaction. In some instances,the line item information may additionally be stored in a memory of theuser computing device 140 for immediate use.

If the user computing device 140 determines at step 414 that thetransaction is flagged as an enhanced transaction then, at step 422, theuser computing device 140 may send a request to the transaction server110 to retrieve, from the database 130, the line item informationassociated with the selected transaction.

At step 424, the transaction server 110 cause the line item informationassociated with the selected transaction to be retrieved from thedatabase 130.

At step 426, the transaction server 110 may send the line iteminformation to the user computing device 140 or may otherwise cause theline item details to be displayed in by the user computing device 140via the banking application 111.

At step 428, the user computing device 140 may receive the line iteminformation associated with the selected transaction and may use theline item information to generate a digital receipt associated with theselected transaction for display in the banking application 111. Forinstance, as shown in FIG. 5D, the user computing device 140 may causethe banking application 111 to output a user interface 500 d displayinga digital receipt for the selected transaction including the line iteminformation associated with the transaction.

Referring to FIG. 4C, at step 430, the user computing device 140 mayreceive a user selection requesting that one or more portions of thereceipt or transaction be delegated to one or more individuals. Forinstance, the user computing device 140 may receive an indication of aselection of option 523 shown in user interface 500 d in FIG. 5D.

At step 432, in response to the user selection requesting that one ormore portions of the receipt or the selected transaction be delegated toone or more individuals, the user computing device 140 may cause thebanking application 111 to output a user interface displaying a list ofcontacts from which the user may select individuals to whom portions ofthe receipt or portions of the transaction should be delegated. Forinstance, the user computing device 140 may request permission from theuser to access the user's contacts stored in a memory of the usercomputing device 140 and/or at a memory source accessible by the usercomputing device 140 and/or to access and analyze an account, such as asocial media account, email account, or the like, associated with theuser to obtain contacts and corresponding contact information. In somecases, the user computing device 140 may query a third-party service toobtain the contact information, such as a phone number, email address,social media handle, or the like. The user computing device 140 maygenerate a list of those contacts and corresponding contact informationand may output the list via the banking application 111, such as shownin user interface 500 e shown in FIG. 5E.

At step 434, the user computing device 140 may receive an indication ofa user selection of one or more of the contacts for delegating one ormore portions of the receipt or transaction, as shown in FIG. 5E.

At step 436, the user computing device 140 may cause the bankingapplication 111 to output a user interface that displays each of theselected one or more contacts and options for receiving user inputsindicating one or more portions of the receipt to be delegated to eachof the selected one or more contacts. For instance, the user computingdevice 140 may cause the banking application 111 to generate a userinterface such as user interface 500 f shown in FIG. 5F. The user mayselect individual items from the receipt to delegate to each of theselected individuals. In some cases, the user may allocate to theselected individual a full payment amount for a particular item or mayallocate a partial payment amount for the particular item. In someinstances, the user need not delegate particular items to the selectedindividuals, and may instead input a particular dollar amount associatedwith the transaction or receipt, or a particular percentage of the totalof the transaction or receipt.

After the user has indicated the manner in which the receipt items andpayment amounts should be delegated, at step 438, the user computingdevice 140 may automatically perform certain calculations associatedwith the request to delegate payment. For instance, the user computingdevice 140, where applicable, may calculate a portion of any tax and/ortip to allocate to each of the selected individuals. The user computingdevice 140 may cause an equal portion to be allocated to each individualor, in some cases, may cause the banking application 111 to provide anoption in the user interface to receive a user input of a particularamount of each the tax and/or the tip to allocate to the selectedindividuals, and the user may input a particular dollar amount or apercentage of the total of the tax and/or the tip. The user computingdevice 140 may additionally perform other calculations. For instance, ifthe user is requesting payment from more than one individual, the usercomputing device 140 may confirm that the total requested amount doesnot exceed a total amount associated with the selected transaction. Inthe event that the total requested amount does exceed the total amountassociated with the selected transaction, the user computing device 140may cause the banking application 111 to output a user interfacedisplaying an error message and instructions to the user to correct therequested amounts. After the user has made any necessary corrections,the user computing device 140 may cause the banking application 111 tooutput a user interface that displays a total amount to be delegated toeach of the selected individuals and may display an option for the userto submit the request.

Referring to FIG. 4D, at step 440, upon receiving, at the user computingdevice 140 and via the banking application 111, an indication of a userselection to submit the request to delegate payment of the selectedtransaction, the user computing device 140 may transmit informationassociated with the request to the payment delegation server 120. Theinformation sent to the payment delegation server 120 may includeinformation identifying the transaction being delegated. The computingdevice 140 may retrieve, from the transaction server 110 and/or thedatabase 130, information associated with the transaction to be deleted.For instance, computing device 140 may retrieve and include in thedelegation request a transaction identifier, which uniquely identifiesthe transaction being delegated, a transaction description, atransaction value or amount, a transaction date, or the like. Theinformation may additionally include the details associated with theindividuals to whom payment is being delegated, such as the delegate'sname and contact information, e.g., email address, phone number, socialmedia handle, etc., and a total amount delegated to each delegate. Theinformation may additionally include details about the individualtransaction line items delegated to each delegate, such as adescription, and the amount delegated for each individual transactionline item, tax associated with the transaction line item, a portion ofthe tip associated with the transaction line item, or the like.

At step 442, the payment delegation server 120 may receive theinformation associated with the request to delegate payment for theselected transaction.

At step 444, the payment delegation server 120 may generate a uniquepayment token for the transaction identified in the delegationinformation received from the user computing device 140. The paymentdelegation server 120 may identify the transaction in the database 130by the transaction identifier included in the delegation information andmay update the transaction record in the database 130 to indicate thegenerated payment token. The payment delegation server 140 may update amemo, discretionary, miscellaneous, or other unused field associatedwith the transaction record with the payment token. The payment tokenmay be used to associate the original transaction with subsequentpayments received from the delegates. In some cases, the payment tokenmay comprise a URL link to a script configured to access informationassociated with delegation requests associated with the transaction. Thepayment token link may be compressed using, for example, a URL shortenerto reduce the length of the link for convenience in transmission.

At step 446, the payment delegation server 120 may generate a delegationrequest for each delegate identified in the delegation information. Thedelegation request may be associated with the transaction beingdelegated and may include information, from the received delegationinformation, that pertains to the particular delegate. For example, thedelegation request may include a delegation request identifier, thetransaction identifier, a total payment amount or value delegated to thedelegate and/or information identifying the individual transaction lineitems and associated amounts delegated to the individual delegate,and/or contact information for the delegate. The delegation request maybe stored in the database 130.

At step 448, the payment delegation server 120 may generate a paymentURL for each of the generated delegation requests. The payment URL mayinclude one or more parameters containing information associated withthe delegation request. For instance, the URL parameters may includeinformation identifying the individual requesting the payment; the totalpayment amount delegated to the delegate and/or the informationidentifying the individual transaction line items and associated amountsdelegated to the delegate; and/or information identifying where paymentfrom the delegate should be sent—such as a bank routing number, a bankaccount number, a credit card number, or the like associated with theuser's original form of payment. In some instances, the informationidentifying where payment should be sent may simply be an email addressor phone number of the requesting user, which may be used when paymentfrom the delegate is received at the user's bank to access the user'sbank account number or credit card number from a secure source, such asthe transaction server 110. The URL parameters may additionally includethe payment token generated by the payment delegation server 120 for thedelegated transaction. One or more of the URL parameters may beencrypted to ensure security of sensitive information duringtransmission. In some instances, rather than include all of theaforementioned information in various URL parameters, the payment tokenitself, included in a parameter of the payment URL, may comprise a URLlink to a script configured to request or retrieve the aforementionedinformation. For instance the payment token link may execute a scriptconfigured to request or retrieve, from the payment delegation server120 or the database 130, some or all of the aforementioned information,such as from the stored delegation request. The payment URL mayadditionally execute a script configured to initiate a payment processfrom the delegate to the user.

At step 450, the payment delegation server 120 may transmit thegenerated payment URLs back to the user computing device 140 fortransmission to each of the corresponding delegates; and at step 452,the user computing device 140 may receive the generated payment URLs.

In some instances, the user computing device 140 or the transactionserver 110 may perform some or all of the above-noted functionsdescribed in steps 442-450 as being performed by the payment delegationserver 120.

Referring to FIG. 4E, at step 454, the user computing device 140 maygenerate and transmit a delegation message to each of the delegatesusing the contact information provided in the delegation request forthat delegate and including the corresponding payment URL generated bythe payment delegation server 120. The delegation message may requestpayment for the delegated portions of the transaction indicated in thedelegation request. The message may, in some instances, itemize theindividual items delegated to the delegate and the associated amounts.The message may additionally, in some instances, include the totalamount that the user has requested be delegated to the delegate.

At step 456, the delegate may receive the delegation message transmittedfrom the payment delegation server 120 at a device used by the delegate,such as the delegate computing device 150. For instance, the delegatecomputing device 150 may receive a delegation message, such asdelegation message 500 g shown in FIG. 5G. In the case where thedelegate also has the banking application 111 installed at the delegatecomputing device 150 or has website access to the banking application111, the delegation message may be output via a user interface of thebanking application 111. Alternatively or additionally, the delegationmessage may be received as an email, a text, via social media, or thelike. The delegation message may display the details of the delegationrequest and the payment URL. In some instances, the details of thedelegation request may be displayed upon accessing the payment URL. Thedelegation message may include options to accept, decline, or transferthe delegation request to another individual. The delegate may selectone of the options, and the requesting user may be notified of theselected option. In the case of transferring the delegation request, thetransfer option may provide a user interface for receiving contactinformation, such as an email address or a phone number, of asub-delegate and receiving an amount to be delegated to thesub-delegate. Upon submission of a request to transfer the delegationrequest, a script may be executed to update the delegation requeststored in the database 130 with information associated with thesub-delegate or to generate a new delegation request associated with thesub-delegate. The updated or new delegation request may be stored in thedatabase 130 and a delegation message may be transmitted to thesub-delegate for payment of the delegated amount. Any payment made bythe sub-delegate may be paid to the original requesting user.

At step 458, if the delegate decides the accept the delegation request,the delegate may access the payment URL by clicking on the linkdisplayed in the delegation message, such as link 529 shown in FIG. 5G,or by copying and pasting the link into a web browser. Accessing thelink may cause a payment process to be initiated for submitting paymentfrom the delegate to the requesting user. For instance, accessing thelink may trigger the execution of a script at the delegate computingdevice 150. The script may cause an application or website associatedwith a default payment method associated with the delegate computingdevice 150 to be identified and executed. Alternatively or additionally,the script may cause a request to be output at the delegate computingdevice 150 for the delegate to select a preferred payment methodapplication for using in making payment to the user.

At step 460, the delegate computing device 150 may execute theapplication or website associated with the default or selected paymentmethod, such as shown in FIG. 5H. The script may call one or more APIsfor interfacing with the payment application or website. The scriptand/or the API may cause one or more fields associated with the paymentapplication or website to be prepopulated with the payment informationassociated with the delegation request, such as a payment amount andrecipient information identifying where payment should be made. Therecipient information need not be sensitive financial information, suchas a bank account or credit card number of the user, and instead may beinformation identifying the user who initiated the delegation request byan email address or a phone number associated with the user, which maylater be used at a secure source device, such as the transaction server110, to access the user's financial information. The delegate may adjustthe prepopulated fields as needed. For instance the delegate may adjustthe payment amount to enter a different amount.

At step 462, the script and/or API executing at the delegate device 150may additionally determine whether to adjust the payment amount from theamount requested in the delegation request to a different amount. Suchan adjustment may be necessary if delegation requests for a selectedtransaction were sent to more than one delegate and one or more of thedelegates made a payment exceeding their respective requested amount,thus causing the remaining amount, of the total requested, needing to bepaid by a final delegate to be less than the amount the requesting useroriginally requested. For instance, referring to FIGS. 5E-5G, assumeBob's portion of the $86.46 restaurant bill was $24.17, Brandon'sportion was $24.82, and Mary's portion was $37.47. If Bob sentdelegation requests to both Brandon and Mary for their respectiveamounts, and Mary was the first to submit payment, and she decided tocontribute more to the bill than requested by Bob, then the amountBrandon needs to pay may be adjusted downward to account for the extraamount Mary contributed. For example, if Mary submitted a payment for$40.00 instead of $37.47, the difference between her actual paymentamount and the requested amount, i.e., $2.53, may be subtracted from theamount Brandon needs to pay—thus adjusting his amount from the requestedamount of $24.82 to adjusted amount of $22.29. The script and/or API maycause this adjustment to be made when Brandon attempts to make hispayment. For instance, prior to the delegate's submission of payment,the script and/or API may query the payment delegation server 120 todetermine if the requested payment amount for the delegate exceeds anoutstanding or remaining amount to be paid toward the delegatedtransaction. If the requested payment amount exceeds the remainingamount to be paid toward the delegated transaction, the delegate'spayment amount may be adjusted, such as shown in FIG. 5H.

At step 464, the script and/or API executing at the delegate computingdevice 150 may additionally cause a payment transaction generated by thedelegate's payment method to be embedded with the payment token that wasincluded in the payment URL. The script and/or API may cause the paymenttoken to be embedded or stored in a field of the payment transactionrecord prior to the delegate submitting the payment transaction.Alternatively, the script and/or API may cause the payment token to beembedded in the payment transaction record upon receiving an indicationthat the delegate has submitted the payment transaction. The paymenttransaction record may comprise a number of fields and structure inaccordance with a standard format used by the payment processing system160. For instance, for an ACH network payment processing system, thepayment transaction record may comprise a structure and layoutconsistent with the National Automated Clearing House Association(NACHA) standard ACH entry detail and/or entry detail addenda records.The script and/or API may cause the payment token to be stored in one ofthe standard fields of the transaction record—such as a memo,discretionary, miscellaneous, or other unused field of the paymenttransaction record. For instance, if the delegate chooses to make an ACHpayment to the user, the payment token may be embedded in one of thestandard unused fields of the ACH entry detail or entry detail addendatransaction records. For instance, as shown in FIG. 6A, the paymenttoken may be stored in discretionary data field 610 of the paymenttransaction record. In some instances, where the discretionary datafield 610 is being used for some other purpose, such as a memo fieldthat has text included from the delegate, the payment token may bestored in a miscellaneous or other field, such as miscellaneousinformation field 620, of an addendum record associated with thetransaction, such as shown in FIG. 6B. When the payment transaction istransmitted to the payment processing system 160 and eventually arrivesat the user's bank, the payment token may be detected in the paymenttransaction record and may be used to link the delegate payment back tothe original transaction.

Referring to FIG. 4F, at step 466, upon receiving an indication at thedelegate computing device 150 that the delegate has submitted payment,the delegate computing device 150 may transmit the payment transactionrecord to the payment processing system 160.

At step 468, the payment processing system 160 may receive the paymenttransaction record associated with the payment made by the delegate tothe requesting user. The payment processing system 160 may coordinate asettlement process between a bank associated with the delegate and abank associated with the requesting user.

At step 470, the payment processing system 160 may coordinate sendingpayment transaction record associated with the delegate's paymenttransaction to the requesting user's bank so funds for payment may bedebited from the delegate's selected payment account and transmitted tothe bank associated with the requesting user.

For instance, at step 472, the transaction server 110 may ultimatelyreceive the payment transaction record associated with the delegate'spayment and may credit the requesting user's payment account with thepayment amount. The received payment transaction record may be embeddedwith the payment token stored therein at step 464.

In receiving and crediting the requesting user's payment account, atstep 474, the transaction server 110 may detect the payment token in thepayment transaction record. Detection of the payment token in thepayment transaction record may serve as an indication that the paymenttransaction is a payment associated with a delegation request made bythe user. The transaction server 110 may distinguish the payment tokenfrom other miscellaneous text that might otherwise be included in thepayment transaction record (such as when the payment token is embeddedin a memo field) based on an expected format of the payment token orbased on successfully decoding the suspected payment token.

At step 476, the transaction server 110 may send, to the paymentdelegation server 120, payment information associated with the receivedpayment transaction record and, at step 478, the payment delegationserver 120 may receive the payment information. The payment informationmay include information such as a transaction identifier, a delegatename, contact information, or other identifier, a payment amount, a datereceived, a date posted, any note included in the transaction from thedelegate, and the payment token that was embedded in the paymenttransaction record.

Upon receiving the payment transaction information, at step 480, thepayment delegation server 120 may use the payment token to link thepayment transaction with the original delegated transaction. Forinstance, the payment delegation server 120 may query the database 130,using the payment token, to identify the original delegated transactionhaving the same payment token stored therewith. The payment delegationserver 120 may store, in association with the original transaction, thetransaction identifier identifying the received payment transaction sothat the payment transaction received from the delegate may be linkedwith the original transaction for which the user requested/delegatedpayment. The payment delegation server 120 may additionally update thecorresponding stored delegation request to indicate that payment hasbeen received from the delegate.

Referring to FIG. 4G, at step 482, after identifying the originaltransaction and linking the received payment transaction from thedelegate to the original transaction, the payment delegation server 120may cause a notification to be sent to the user notifying that a paymentassociated with a delegation request has been received. For instance,the payment delegation server 120 may send an email or a text message tothe user, or may output a notification at the user computing device 140,via the banking application 111, notifying of receipt of a payment fromthe delegate.

At step 484, the user may receive the notification at the user computingdevice 140. For instance, the user may receive the notification via auser interface, such as user interface 500 i shown in FIG. 5I, output atthe banking application 111 executing on the user computing device 140.The notification may include a link, such as link 531, to the originaltransaction. Additionally or alternatively, the user may access theoriginal transaction through a transaction viewing user interface of thebanking application 111, such user interface 500 a shown in FIG. 5A.

At step 486, the user computing device 140 may receive a request to viewthe original transaction and, at step 488, the user computing device 140may cause the banking application 111 to output a user interfacedisplaying a transaction summary comprising the original transactionwith any received delegate payment transactions attached thereto. Forinstance, the user computing device 140 may cause the bankingapplication 111 to output a user interface such as user interface 500 jshown in FIG. 5J. The user interface may display the received paymenttransactions underneath the original transaction, for example, toindicate that the received payment transactions are associated with theoriginal transaction. In some instances, the user may be able to selectto original transaction and an option to view associated receiveddelegated payments, and a list of delegated payments may be displayed.In some instances, the user may be able to select the transaction andalso view pending delegate requests, e.g., those for which delegateshave not yet sent payment. The user may be able to modify pendingdelegate requests to remove requests, adjust amounts, add additionaldelegates, or the like. In accordance with aspects of this disclosure, auser is able to efficiently and conveniently track, view, and managereceived and/or pending payments associated with requests to split ordelegate portions of a payment for a transaction.

In some instances, rather than the user generating and sendingdelegation requests to one or more individuals, the one or moreindividuals may instead proactively push payments to the user. Forexample, as described above with respect to steps 416-426, the user mayscan a receipt, such as a bill from a restaurant, including a bar codeor QR code, and the bar/QR code may be used to retrieve line iteminformation associated with the transaction on the receipt. Forinstance, descriptions, prices, quantities, etc. of the various itemspurchased at the restaurant may be retrieved. The bar code or QR codemay have embedded therein a link which calls a script to retrieve orrequest the line item details from a merchant device, and thecorresponding line item details may be received and stored together inthe database 130 with the original transaction to enhance thetransaction. The enhanced transaction may further be used to generate adigital receipt, as described at step 428. In some cases, the paymenttoken discussed above, which uniquely identifies an original transactionfor linking with subsequent payment transactions, may be generated whenthe line item information is received and stored with the originaltransaction, rather then when the user submits the delegation request asdiscussed above. In the case where the payment token is generated uponreceiving the line item information, the payment token may be embeddedin the original transaction in a memo or other unused field of theoriginal transaction in the same manner as described above. After theuser has scanned the bar/QR code from the receipt and the originaltransaction is enhanced with the line item information, otherindividuals who may be co-located with the user and who also haveinstalled on their devices, or have access to, the banking application111 may also scan the bar/QR code from the same receipt. For instance,the user's friends with whom he shared a meal at the restaurant may scanthe receipt after the user has scanned the receipt and paid for thetransaction, so that each of the friends can send a payment to the userfor their own portion of the meal. When the other individuals scan thebar/QR code, via the banking application 111, the script associated withthe bar/QR code may, prior to requesting any line item information froma merchant device, first cause the database 130 to be queried todetermine whether the line item information has already been retrievedand stored with an original transaction. The script may query thedatabase 130 using identification information embedded in the bar/QRcode—such as a unique transaction identifier, merchant name, merchantlocation, date/time of transaction, transaction amount, payment method,etc. or a combination thereof, to identify the original transaction anddetermine if it has already been enhanced with the line iteminformation. If the script identifies the original transaction anddetermines that the line item information has already been retrieved andassociated with the original transaction in the database 130, the scriptmay retrieve and transmit to the individual's device the payment tokenthat was generated when the line item information was originallyreceived and stored, and information identifying the payor associatedwith the original transaction.

The script may also use the enhanced transaction to generate a digitalreceipt for display at the individual's device. Alternatively oradditionally, instead of the individually scanning the receipt, the userwho made the payment may transmit the generated digital receipt to theother individuals. For instance, the user may email or text the digitalreceipt to the individual, or may transmit the receipt from the user'sdevice to the individual's device via a short-range communicationprotocol, such as Bluetooth, near-field communication (NFC), or thelike. In some cases, the payment token may alternatively be generatedand stored in the original transaction when the user transmits thegenerated digital receipt to another individual.

Upon receiving the digital receipt and the payment token at theindividual's device, the digital receipt may be displayed in a userinterface of the banking application 111, and the individual may selectindividual items from the digital receipt for which the individual wouldlike to make payment. The script may further cause a default paymentapplication to execute at the individual's device and may initiatepayment for the selected items to the paying user, using the retrievedinformation identifying the payor associated with the originaltransaction. The script may further cause a payment transaction recordgenerated by the individual's payment method to be embedded with thepayment token and payment may be made to the user in the mannerdescribed with respect to steps 460 to 488.

While the above descriptions of FIGS. 4A-4G, 5A-5J, and 6A-6B describethe banking application 111 as being accessed and executed at the usingcomputing device 140 to perform the various payment delegation andlinking functions, alternatively or additionally, the bankingapplication 111 may be accessed and executed via the transaction server110, such as when a user accesses the banking application via a websiteassociated with the transaction server 110, and the transaction server110 may perform some or all of the various functions described above asbeing performed by the user computing device 140.

One or more aspects disclosed herein may be embodied in computer-usableor readable data and/or computer-executable instructions, such as in oneor more program modules, executed by one or more computers or otherdevices as described herein. Generally, program modules includeroutines, programs, objects, components, data structures, or the likethat perform particular tasks or implement particular abstract datatypes when executed by a processor in a computer or other device. Themodules may be written in a source code programming language that issubsequently compiled for execution, or may be written in a scriptinglanguage, such as (but not limited to) HTML or XML. Thecomputer-executable instructions may be stored on a computer-readablemedium, such as a hard disk, optical disk, removable storage media,solid-state memory, RAM, or the like. As will be appreciated by one ofskill in the art, the functionality of the program modules may becombined or distributed as desired in various embodiments. In addition,the functionality may be embodied in whole, or in part, in firmware orhardware equivalents such as integrated circuits, field programmablegate arrays (FPGA), or the like. Particular data structures may be usedto more effectively implement one or more aspects disclosed herein, andsuch data structures are contemplated within the scope ofcomputer-executable instructions and computer-usable data describedherein. Various aspects disclosed herein may be embodied as a method, acomputing device, a system, and/or a computer program product.

Although the present invention has been described in certain specificaspects, many additional modifications and variations would be apparentto those skilled in the art. In particular, any of the various processesdescribed above may be performed in alternative sequences and/or inparallel (on different computing devices) in order to achieve similarresults in a manner that is more appropriate to the requirements of aspecific application. It is therefore to be understood that the presentinvention may be practiced otherwise than specifically described withoutdeparting from the scope and spirit of the present invention. Thus,embodiments of the present invention should be considered in allrespects as illustrative and not restrictive. Accordingly, the scope ofthe invention should be determined not by the embodiments illustrated,but by the appended claims and their equivalents.

What is claimed is:
 1. A computer-implemented method comprising:obtaining first transaction data indicating a first transaction at amerchant, wherein the first transaction data comprises a transactionidentifier and a value of the first transaction; obtaining contactinformation for sending a request for a portion of the value of thefirst transaction; sending, to a payment delegation server, thetransaction identifier and information indicating the portion of thevalue of the first transaction; receiving, from the payment delegationserver, a payment uniform resource locator (URL) comprising a firstparameter indicating the portion of the value of the first transactionand a second parameter indicating a payment token associated with thefirst transaction; transmitting, using the contact information, adelegation request associated with the first transaction and comprisingthe payment URL; obtaining, from a payment processing system, secondtransaction data indicating a second transaction, wherein the secondtransaction data comprises a standardized field comprising the paymenttoken; generating, based on obtaining the second transaction data, anindication of a response to the delegation request associated with thefirst transaction; and generating, based on the indication of theresponse to the delegation request associated with the firsttransaction, a transaction summary comprising the first transaction andthe second transaction.
 2. The computer-implemented method of claim 1,wherein the payment processing system comprises an Automated ClearingHouse (ACH) system.
 3. The computer-implemented method of claim 1,wherein the payment processing system comprises a credit card processingsystem.
 4. The computer-implemented method of claim 1, furthercomprising obtaining the first transaction data by: receiving image datacomprising an image of a receipt associated with the first transaction;and processing the image data to identify the value of the firsttransaction by performing a character recognition process on the imagedata.
 5. The computer-implemented method of claim 1, further comprising:receiving image data comprising an image of a receipt associated withthe first transaction; processing the image data to identify a bar code;and decoding the bar code to obtain the value of the first transaction.6. The computer-implemented method of claim 1, further comprisingobtaining the contact information by: requesting permission to analyze auser account; obtaining permission to analyze the user account; andquerying, based on a contact indicated in the user account, athird-party service to obtain the contact information.
 7. Thecomputer-implemented method of claim 1, wherein: the payment token isencoded using a character encoding; and generating the indication of theresponse comprises decoding the payment token included in the secondtransaction data.
 8. The computer-implemented method of claim 1, whereingenerating the indication of the response to the delegation requestassociated with the first transaction comprises: transmitting, to thepayment delegation server, the second transaction data; and obtaining,from the payment delegation server, an indication that the secondtransaction data is associated with the delegation request associatedwith the first transaction.
 9. An apparatus, comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the apparatus to: obtain first transactiondata indicating a purchase transaction, wherein the first transactiondata comprises a transaction identifier and a value of the purchasetransaction; obtain contact information for sending a request for aportion of the value of the purchase transaction; send, to a paymentdelegation server, the transaction identifier and information indicatingthe portion of the value of the purchase transaction; receive, from thepayment delegation server, a payment uniform resource locator (URL)comprising a first parameter indicating the portion of the value of thepurchase transaction and a second parameter indicating a payment tokenassociated with the purchase transaction; transmit, using the contactinformation, a delegation request associated with the purchasetransaction and comprising the payment URL; obtain, from a paymentprocessing system, second transaction data indicating a paymenttransaction, wherein the second transaction data comprises astandardized field comprising the payment token; transmit, to thepayment delegation server, the second transaction data indicating thepayment transaction; obtain, from the payment delegation server, anindication that the payment transaction is associated with thedelegation request associated with the purchase transaction; andgenerate, based on the indication that the payment transaction isassociated with the delegation request associated with the purchasetransaction, a transaction summary comprising the purchase transactionand the payment transaction.
 10. The apparatus of claim 9, wherein thepayment processing system comprises an Automated Clearing House (ACH)system.
 11. The apparatus of claim 9, wherein the payment processingsystem comprises a credit card processing system.
 12. The apparatus ofclaim 9, wherein the instructions, when executed by the one or moreprocessors, cause the apparatus to obtain the first transaction data by:receiving image data comprising an image of a receipt associated withthe purchase transaction; and processing the image data to identify thevalue of the purchase transaction by performing a character recognitionprocess on the image data.
 13. The apparatus of claim 9, wherein theinstructions, when executed by the one or more processors, cause theapparatus to obtain the first transaction data by: receiving image datacomprising an image of a receipt associated with the purchasetransaction; processing the image data to identify a bar code; anddecoding the bar code to obtain the first transaction data.
 14. Theapparatus of claim 9, wherein the instructions, when executed by the oneor more processors, cause the apparatus to obtain the contactinformation by: requesting permission to analyze a user account;obtaining permission to analyze the user account; and querying, based ona contact indicated in the user account a third-party service to obtainthe contact information indicated in the user account.
 15. The apparatusof claim 9, wherein: the payment token is encoded using a characterencoding; and the instructions, when executed by the one or moreprocessors, further cause the apparatus to: transmit the secondtransaction data to the payment delegation server based on successfullydecoding the payment token received in the second transaction data. 16.A non-transitory, computer-readable medium storing instructions that,when executed by one or more processors, cause the one or moreprocessors to perform steps comprising: obtaining first transaction dataindicating a purchase transaction, wherein the first transaction datacomprises a transaction identifier and a value of the purchasetransaction; receiving a request to delegate a portion of the value ofthe purchase transaction; querying a computing device to obtain contactinformation for sending a request for the portion of the value of thepurchase transaction; sending, to a payment delegation server, thetransaction identifier and information indicating the portion of thevalue of the purchase transaction; receiving, from the paymentdelegation server, a payment uniform resource locator (URL) comprising afirst parameter indicating the portion of the value of the purchasetransaction and a second parameter indicating a payment token associatedwith the purchase transaction; transmitting, using the contactinformation, a delegation request associated with the purchasetransaction and comprising the payment URL; obtaining, from an AutomatedClearing House (ACH) system, second transaction data indicating apayment transaction, wherein the second transaction data comprises astandardized field comprising the payment token; generating, based onobtaining the second transaction data, an indication of receipt of apayment associated with the delegation request associated with thepurchase transaction; and generating, based on the indication of receiptof the payment associated with the delegation request associated withthe purchase transaction, a transaction summary comprising the purchasetransaction and the payment transaction.
 17. The non-transitory,computer-readable medium of claim 16, wherein: the payment token isencoded using a character encoding; and the instructions, when executedby the one or more processors, cause the one or more processors togenerate the indication of receipt of the payment associated with thedelegation request associated with the purchase transaction based onsuccessfully decoding the payment token.
 18. The non-transitory,computer-readable medium of claim 16, wherein the instructions, whenexecuted by the one or more processors, cause the one or more processorsto generate the indication of receipt of the payment associated with thedelegation request associated the purchase transaction by performingsteps comprising: transmitting, to the payment delegation server, thepayment token; and obtaining, from the payment delegation server, anindication that the payment token is associated with the purchasetransaction.
 19. The non-transitory, computer-readable medium of claim16, wherein the instructions, when executed by the one or moreprocessors, cause the one or more processors to obtain the firsttransaction data by performing steps comprising: receiving image datacomprising an image of a receipt associated with the purchasetransaction; and processing the image data to identify the value of thepurchase transaction by performing a character recognition process onthe image data.
 20. The non-transitory, computer-readable medium ofclaim 16, wherein the instructions, when executed by the one or moreprocessors, cause the one or more processors to obtain the firsttransaction data by performing steps comprising: receiving image datacomprising an image of a receipt associated with the purchasetransaction; processing the image data to identify a bar code; anddecoding the bar code to obtain the first transaction data.